> 
> "Eriban" <pov### [at] spamgourmetcom> wrote in message 
> news:web.4a411f4899a5bfb681475b100@news.povray.org...
>>
>> I just thought I'd share my first results of using your rope macro. 
>> Attached is
>> an image with the result. To create the hanging loops I created a 
>> small macro
>> of my own. I still need to clean it up a bit and make it a bit more 
>> general,
>> but then I'll share it.
>>
>> I still have a problem with showing the fibers. When I turn this on, 
>> rendering
>> slows down to a crawl, and the results look pretty bad. Basically, the 
>> rope
>> becomes all black. I could be that I am doing something wrong, or that 
>> the
>> version of MegaPov I am using is not compatible with your macros. I 
>> still need
>> to investigate what's wrong. However, there's no rush, cause in my 
>> scene there's
>> no need to show the fibers anyway.
>>
> 
> Hi Erwin,
> 
> No it's nothing you've done wrong.
> 
> As soon as you said that I remembered that I was surprised that I hadn't 
> needed to increase the POV-Ray max_trace_level when I developed the 
> outer 'fibre' layer, because it uses a sort of semi-transparent skin 
> around the outside of the rope made out of strings of spheres. This 
> semi-transparent layer is why it takes about 10 times as long to render. 
> I developed this under 3.7 beta 32 and I had intended to test it on 
> POV-Ray 3.6 before posting it, but I forgot.
> 
> Now that I tried it on 3.6 it clearly needs the following line adding if 
> fibres are used and I would imagine it's the same problem for MegaPOV:
> global_settings {max_trace_level 10}
> 
> I'm still not really sure why it doesn't need this on the 3.7 beta 32.
> I also notice that the lighting levels are a lot darker on 3.6, but I 
> guess you've already spotted that and set Rope_Brightness to 2 to 
> compensate, because your scene looks bright enough (or maybe MegaPOV is 
> different from 3.6 on lighting levels).
> 
> Best Regards,
> Chris B.
> 

With version 3.7, when a transparent object don't have reflection nor an 
interior with an ior, passing trough such an object don't count toward 
the max_trace limits. That change happened over 10 versions ago, I 
think. Now, a ray can pass trough over 500 transparent object, giving 
over 1000 surfaces intersections.

Alain

Post a reply to this message